Skip to content

Fix edpm_container_registry_logins indentation #1197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renjingxiao wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix edpm_container_registry_logins indentation #1197

renjingxiao wants to merge 1 commit into from
+4 −4

Conversation

@renjingxiao
Copy link
Contributor

@renjingxiao renjingxiao commented Jan 16, 2026

The edmp_container_registry_logins section was generating incorrect indentation in nodeset YAML files, causing 'did not find expected key' errors.

Changed Jinjia2 whitespace control directives to be consistent throughout the template to fix the indentation issue.

@renjingxiao
Fix edpm_container_registry_logins indentation
c1af017 
The edmp_container_registry_logins section was generating
incorrect indentation in nodeset YAML files, causing
'did not find expected key' errors.

Changed Jinjia2 whitespace control directives to be consistent
throughout the template to fix the indentation issue.
@openshift-ci
Copy link

openshift-ci bot commented Jan 16, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sathlan for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link

openshift-ci bot commented Jan 16, 2026

Hi @renjingxiao. Thanks for your PR.

I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

needs-ok-to-test

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@renjingxiao